[NTG-context] Re: The graph is not visible.

2024-04-25 Thread Fabrice Couvreur
e in the >> component chapter-14 : >> >> It is probably not related to the figure itself. Something may be >> different in this component compared to the other ones. I cannot really >> say, of course. Still, using external image instead of inline metapost may >> be fix

[NTG-context] Re: The graph is not visible.

2024-04-25 Thread Fabrice Couvreur
not related to the figure itself. Something may be > different in this component compared to the other ones. I cannot really > say, of course. Still, using external image instead of inline metapost may > be fix it. Not elegant, but if it works it works! > > Good luck, > Taco > > >

[NTG-context] Re: The graph is not visible.

2024-04-25 Thread Taco Hoekwater
itself. Something may be different in this component compared to the other ones. I cannot really say, of course. Still, using external image instead of inline metapost may be fix it. Not elegant, but if it works it works! Good luck, Taco > > \startcomponent[chapter-14] > \startMPpage > .

[NTG-context] Re: The graph is not visible.

2024-04-25 Thread Hans Hagen
On 4/25/2024 4:08 PM, Fabrice Couvreur wrote: Hi Taco, I knew I wouldn't be able to explain what was happening. The code works perfectly and the figure is clearly visible in the component chapter-14 : \startcomponent[chapter-14] \startMPpage ... \stopMPpage \stopcomponent But if I compile my

[NTG-context] Re: The graph is not visible.

2024-04-25 Thread Fabrice Couvreur
Hi Taco, I knew I wouldn't be able to explain what was happening. The code works perfectly and the figure is clearly visible in the component chapter-14 : \startcomponent[chapter-14] \startMPpage ... \stopMPpage \stopcomponent But if I compile my project, it disappears !! \startproduct

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

2023-08-21 Thread Carlos
s > > > > Opening a group with \starttext makes no sense because there is nothing > > after \stoptext. > > > > The possibility to nest \starttext is necessary when you \startproduct etc. > > where components can be be documents on its own and this means

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

2023-08-20 Thread Hans Hagen
is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. begin example \starttext \starttext \stoptext \stoptext end example but this doesn't. begin example \starttext \starttext

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

2023-08-20 Thread Wolfgang Schuster
is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. begin example \starttext \starttext \stoptext \stoptext end example but this doesn't. begin example \starttext \starttext

[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach

2023-08-20 Thread Carlos
Opening a group with \starttext makes no sense because there is nothing after \stoptext. The possibility to nest \starttext is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. > be

[NTG-context] Project structure with nested subfolders and shared environments.

2022-12-15 Thread Pawel Urbanski via ntg-context
\startproject * \usepath [{ Metadata }] \environment Environment.tex \stopproject % /MainFolder/Metadata/Environment.tex \startenvironment * % Test if setup is applied. \setupbodyfont[ebgaramond] \stopenvironment % /MainFolder/SubFolder/SubSubFolder/Doc.tex \startproduct * \project Meta \startcomponent

Re: [NTG-context] Page break with placement of a figure at the bottom of the page

2022-11-13 Thread Fabrice Couvreur via ntg-context
__ > \environment[template.mkiv] \definemargindata[marginfigure][inright] \useMPlibrary[dum] \setupmargindata [marginfigure][command=\vbox,align=middle,stack=yes] \setvariables [headertext] [title={Interrogation écrite}, number={3}, day={8}, month={11}, year={2022}

Re: [NTG-context] Unwanted blank page before page figures when using non-placed (hidden) heads

2022-07-29 Thread cryo shock via ntg-context
me. > > > > Cheers, k > > > > > > %%% START of MWE > > > > \definehead[VisiSection][section] > > \setuphead[VisiSection][number=no] > > > > \definehead[InvisiSection][VisiSection] > > \setuphead[InvisiSection][placehead=no]

Re: [NTG-context] Unwanted blank page before page figures when using non-placed (hidden) heads

2022-07-25 Thread Hans Hagen via ntg-context
=no] \definelist[CustomBMarks] \setupinteraction[state=start] \placebookmarks[VisiSection,InvisiSection,CustomBMarks] \startcomponent * % not a product, no   \startVisiSection[title={Custom Section A}]     Text of Custom Section A   \stopVisiSection   \page   \startVisiSection[title={Custom

[NTG-context] Unwanted blank page before page figures when using non-placed (hidden) heads

2022-07-24 Thread cryo shock via ntg-context
] \placebookmarks[VisiSection,InvisiSection,CustomBMarks] \startcomponent * % not a product, no \startVisiSection[title={Custom Section A}] Text of Custom Section A \stopVisiSection \page \startVisiSection[title={Custom Section B}] Text of Custom Section B \stopVisiSection \startInvisiSection

[NTG-context] \placelistofabbreviations in project structure?

2022-06-19 Thread jbf via ntg-context
is defined and give me the correct result if I write \adjp\ or \infull{adjp} in any one of them. My MWE below for the (as yet not working) abbreviations component that contains the placelist command: \startcomponent 04_abbreviations \project project_Dictionary \startchapter[title={Abbreviations

[NTG-context] Solved: Book setup with LHS-side quotes before chapters/parts, header/footer issues, TOC, etc.

2021-10-26 Thread Gerben Wierda via ntg-context
this: \startcomponent p_partone \product prd_book \project project_book \SectionPrequote{The world is not \rationals, it is \reals\crlf {\tf Gerben Wierda}} \part{Title title title} \PartAbstract{This is a part abstract for a normal part.} \component c_chapter \component c_chapter \stopcomponent

Re: [NTG-context] How not to display the header of the chapter page on the page with the table of contents ?

2021-08-16 Thread Wolfgang Schuster via ntg-context
project Do you need a project file? begin component \project[terminale-environment] \startcomponent[terminale_recurrence] ... \endcomponent end component You ignored the order for \startcomponent and \project. The environment (or project) file has to be loaded *after* \startcomponent

Re: [NTG-context] How not to display the header of the chapter page on the page with the table of contents ?

2021-08-16 Thread Fabrice Couvreur via ntg-context
[terminale_recurrence] ... \stopbodymatter \stopdocument \stopproduct end product begin project \startproject[terminale-environment] \environment[terminale-style] ... \stopproject end project begin component \project[terminale-environment] \startcomponent[terminale_recurrence

Re: [NTG-context] How not to display the header of the chapter page on the page with the table of contents ?

2021-08-15 Thread Wolfgang Schuster via ntg-context
it. Another approach would be: [...] Setting values for \title is a way to avoid the chapter setup for the table of contents etc. but there is a way to set values which are used only when you process a component file. To make it work one has to load the environment file after \startcomponent

Re: [NTG-context] Moving the old book-structure to a recent ConTeXt

2021-07-18 Thread Wolfgang Schuster
form to older way, where you passed it without the brackets. Both \component document-xxx and \component [document-xxx] are valid and you can use whatever you prefer. 3. Position of \environment In my example I load the environment-file after \startproduct and \startcomponent

Re: [NTG-context] \startcomponent [*]

2021-03-10 Thread Hans Hagen
On 3/10/2021 5:56 PM, Wolfgang Schuster wrote: Hi, when the wildcard symbol is used as argument to \startcomponent (or \startproduct) the name of the folder is now used and not the file name. \startcomponent * \quotation{\currentcomponent} \stopcomponent it's programmed that way (must have

[NTG-context] \startcomponent [*]

2021-03-10 Thread Wolfgang Schuster
Hi, when the wildcard symbol is used as argument to \startcomponent (or \startproduct) the name of the folder is now used and not the file name. \startcomponent * \quotation{\currentcomponent} \stopcomponent Wolfgang

[NTG-context] Fwd: Re: LMTX 2021.03.02 | cross reference to an external file | \pagereference

2021-03-04 Thread Richard Mahoney
testproject \startbodymatter \component boo.tex \stopbodymatter \stopproduct % master001.tex -- LMTX 2021.03.02 \startproduct testproduct001 \project testproject \startbodymatter \component foo.tex \stopbodymatter \stopproduct % boo.tex -- LMTX 2021.03.02 \startcomponent boo \project

Re: [NTG-context] Project Structure - inheritance rules for environments

2021-03-01 Thread Wolfgang Schuster
only one file but this is seldom needed. begin product.tex \startproduct * \environment environment \component component_1 \component component_2 \stopproduct end product.tex begin component_1.tex \startcomponent * \environment environment ... \stopcomponent end

Re: [NTG-context] \setupuserpagenumber not working as expected

2020-09-06 Thread Jan Willem Flamma
hould be able to copy and adapt to your needs. There are lot of things which can be improved in your example. 1. Pass the filename of the component/product to \startcomponent and not some dummy name (or just use *), this allows you to print the filename with \currentcomponent or \currentproduct

Re: [NTG-context] \setupuserpagenumber not working as expected

2020-09-04 Thread Wolfgang Schuster
the filename of the component/product to \startcomponent and not some dummy name (or just use *), this allows you to print the filename with \currentcomponent or \currentproduct 2. Use \setvariables or \setupdocument to set the document title, revision etc. 3. Use \startsectionblockenvironment to move

Re: [NTG-context] \setupuserpagenumber not working as expected

2020-09-04 Thread Jan Willem Flamma
umbers]\definestructureconversionset    [appendix:pagenumber] [][numbers]=   The fm-frontpage.tex file====\startcomponent currentcomponent \product product % Front page layout\startstandardmakeup % Place logo centered on page\framed[height=5cm,width=broad,frame=off]{\external

Re: [NTG-context] \setupuserpagenumber not working as expected

2020-09-03 Thread jbf
] \definestructureconversionset [appendix:pagenumber] [][numbers] = *The fm-frontpage.tex file* \startcomponent currentcomponent \product product % Front page layout \startstandardmakeup % Place logo centered on page \framed[height=5cm,width=broad,frame=off] {\externalfigure

Re: [NTG-context] \setupuserpagenumber not working as expected

2020-09-03 Thread Jan Willem Flamma
\startcomponent currentcomponent \product product % Front page layout\startstandardmakeup % Place logo centered on page \framed[height=5cm,width=broad,frame=off] {\externalfigure[frontpage-logo.png][width=12cm]} % Place course titles\blank[6*big]\color[Modu_Blue]{\midaligned{\bfc \MyManual

Re: [NTG-context] Compile only one new component in a project

2020-05-07 Thread Wolfgang Schuster
can use a project file where you load all environments and load then the project file in your product and component files. ##chapter-4-seconde.tex## \startcomponent chapter-4-seconde Add here \environment ... or \project ... \startchapter[title=] ... \stopchapter \stopcomponent Wolfgang

Re: [NTG-context] Compile only one new component in a project

2020-05-07 Thread Fabrice Couvreur
Hi Aditya, It does not work ; the compilation encounters errors with each command that I created. I guess it comes from the components. Fabrice ##chapter-4-seconde.tex## \startcomponent chapter-4-seconde \startchapter[title=] ... \stopchapter \stopcomponent Le jeu. 7 mai 2020 à 16:01, Aditya

Re: [NTG-context] \definehead behaving differently when in an environment file versus \input'ed

2020-05-02 Thread Wolfgang Schuster
issue of the journal in one go. (I would simply comment out the \input line and add \startproject \startcomponent etc lines as necessary from each received article.) Problem: I've created a custom chapter heading, but the font size changes depending on whether I'm processing the \input version

[NTG-context] \definehead behaving differently when in an environment file versus \input'ed

2020-05-02 Thread ntg
comment out the \input line and add \startproject \startcomponent etc lines as necessary from each received article.) Problem: I've created a custom chapter heading, but the font size changes depending on whether I'm processing the \input version of the article or the \component version and I

[NTG-context] Questions regarding project structure

2019-05-15 Thread Denis Maier
``` - test_prod.tex ``` \startproduct * \project test \startalignment[middle] HEY \stopalignment \component test_comp \stopproduct ``` - test_comp.tex ``` \startcomponent * \product test_prod % \project test_project % uncomment this to use the \section{Test} \input ward \stopcomponent ``` >F

[NTG-context] Expanding text across two table cells

2019-04-08 Thread Todd DeVries
of these fields should span two cells in the table and wrap to the full width. Currently, they wrap to the width of the first table column. The cells appear to be spanned correctly, but the text does not extend. What am I missing? Thank you for the assistance. \startcomponent c_DATE_clientcode_progress

Re: [NTG-context] problem with \sym?

2019-02-04 Thread Wolfgang Schuster
etuplines[before={}, after={}] \startlines}, after={\stoplines}] \setupCList[2][n, broad, packed, joinedup, autointro] [itemalign=flushright, left={}, right={}, stopper={}, margin=0pc, ] \startcomponent[*] \startCList \sym{} Preface \sym{0.} Prolegomena %<——line 22 \stopCList \stopcomponent

Re: [NTG-context] problem with \sym?

2019-02-04 Thread Wolfgang Schuster
\leaderfill{\leaders\hbox to 1em{\hss. \hss}\hfill} \define[1]\pg{{\switchtobodyfont[10pt]\hfill\at[#1]\crlf}} \startcomponent%\starttext \startCList \sym{} Illustrations and Tables\pg{Illustrations} \sym{} Preface\pg{Preface} \sym{} Acknowledgments\pg{Acknowledgments} \blank[big, fixed] \sym{0

Re: [NTG-context] \everystarttext in components

2018-11-27 Thread Wolfgang Schuster
remember. When you load the environment before \startcomponent etc. you add your command to the token register before it is flushed but when you load the environment after \startcomponent etc. the register is flushed before you add them. This doesn’t mean you should use \everystarttext

Re: [NTG-context] \everystarttext in components

2018-11-27 Thread Wolfgang Schuster
Marco Patzer schrieb am 27.11.18 um 18:34: On Tue, 27 Nov 2018 18:21:45 +0100 Hans Hagen wrote: MWE: \startcomponent * \appendtoks Foobar \to\everystarttext \startdocument\null\stopdocument \stopcomponent If the first and last line is commented out, it prints “Foobar”, when

Re: [NTG-context] \everystarttext in components

2018-11-27 Thread Marco Patzer
On Tue, 27 Nov 2018 18:21:45 +0100 Hans Hagen wrote: > > MWE: > > > > \startcomponent * > >\appendtoks Foobar \to\everystarttext > >\startdocument\null\stopdocument > > \stopcomponent > > > > If the first and last line is comm

Re: [NTG-context] \everystarttext in components

2018-11-27 Thread Hans Hagen
? MWE: \startcomponent * \appendtoks Foobar \to\everystarttext \startdocument\null\stopdocument \stopcomponent If the first and last line is commented out, it prints “Foobar”, when compiled as a component it doesn't. it kicks in when context things a text starts (so earler in this case

[NTG-context] \everystarttext in components

2018-11-27 Thread Marco Patzer
Hi! I've got an issue with my documents after updating context (to 2018.11.18 14:07). I believe it has something to do with \everystarttext. But I'm still digging. Question: Is it intended behaviour that \everystarttext doesn't work in components? MWE: \startcomponent * \appendtoks Foobar

Re: [NTG-context] Need help with project: TeX capacity exceeded

2018-10-05 Thread Wolfgang Schuster
. The same happens here. I discovered it works OK if I move the \product to within the \startcomponent, and I assume that is how it supposed to work: \startcomponent \product prd_1 … \stopcomponent At a guess, I think the wiki page is wrong. But before editing that, I would like to have

Re: [NTG-context] Need help with project: TeX capacity exceeded

2018-10-04 Thread Axel Kielhorn
ave different names. Right now that’s just a limitation of the word processor. > That said, it is definitely not your installation or understanding of the > wiki page that creates the circular inclusion. The same happens here. I > discovered it works OK if I move the \product to within the \sta

Re: [NTG-context] Need help with project: TeX capacity exceeded

2018-10-04 Thread Taco Hoekwater
at creates the circular inclusion. The same happens here. I discovered it works OK if I move the \product to within the \startcomponent, and I assume that is how it supposed to work: \startcomponent \product prd_1 … \stopcomponent At a guess, I think the wiki page is wrong. But bef

Re: [NTG-context] list of figures

2018-09-14 Thread Andrea Valle
% chapter >> >> \input c_2_conceptions.tex >> >> etc > > The ConTeXt way of doing this is: > > \component c_1_semiotics > > \component c_2_conceptions > > also putting > > \startcomponent c_1_semiotics > ... > \stopcomponent > > at the b

Re: [NTG-context] list of figures

2018-09-14 Thread Alan Braslau
% chapter > > \input c_2_conceptions.tex > > etc The ConTeXt way of doing this is: \component c_1_semiotics \component c_2_conceptions also putting \startcomponent c_1_semiotics ... \stopcomponent at the beginning and end in each component file. This project/product scheme is handled more c

Re: [NTG-context] future versions - synctex

2018-08-21 Thread Hans Hagen
before \starttext (\enabledirectives[system.synctex] after \starttext (\startcomponent) should be ignored?) - that could cause hooking picked Lua functions (or taking their "synctex-on" alternatives) - so normally (with synctex off) there wouldn't be any performance impact; worse

Re: [NTG-context] future versions - synctex

2018-08-21 Thread Procházka Lukáš Ing .
hen synctex is turned off. Synctex should be turned on/off before source files are compiled into PDF - via command line option "--synctex" or \enabledirectives[system.synctex] before \starttext (\enabledirectives[system.synctex] after \starttext (\startcomponent) should be

Re: [NTG-context] Questions about \starttext

2018-04-02 Thread John Culleton
text % this text is in bold, too. \stoptext Is this the expected behaviour, or not? Opening a group with \starttext makes no sense because there is nothing after \stoptext. The possibility to nest \starttext is necessary when you \startproduct etc. where components can be be documents on its ow

Re: [NTG-context] Questions about \starttext

2018-04-02 Thread John Culleton
uments on its own and this means \startcomponent includes \starttext in its definition. The second interesting thing is that the unbalanced document is compiled without protests: Minimal example #1 (tested on TL2015, TL2016, TL2017, current CTX from the Garden): \starttext text % in this case,

Re: [NTG-context] Questions about \starttext

2018-04-02 Thread Wolfgang Schuster
t etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. The second interesting thing is that the unbalanced document is compiled without protests: Minimal example #1 (tested on TL2015, TL2016, TL2017, current CTX from the

Re: [NTG-context] Problem with Lua: context.component()

2018-02-23 Thread Hans Hagen
On 2/23/2018 3:26 PM, Procházka Lukáš Ing. wrote: Hello, suppose having: t1.mkiv \starttext   a   \startluacode     context.setvalue("b", "bbb")     context.setvalue("c", 2)     context.component("t2.mkiv")   \stopluacode \stoptext and

[NTG-context] Problem with Lua: context.component()

2018-02-23 Thread Procházka Lukáš Ing .
Hello, suppose having: t1.mkiv \starttext a \startluacode context.setvalue("b", "bbb") context.setvalue("c", 2) context.component("t2.mkiv") \stopluacode \stoptext and t2.mkiv \startcomponent * \b\c \stopcom

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-19 Thread Jean-Pierre Delange
passed to the dm-1.tex file (font, footer) but not the header. > \startcomponent dm-1 > > \component MyLayout > > \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m} > > \input knuth > > \stopcomponent Two things: 1. Use \environment MyLayout instead of \compone

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-19 Thread Fabrice Couvreur
>> I have tried many approaches, but it still does not work. Everything is >> passed to the dm-1.tex file (font, footer) but not the header. >> > > > \startcomponent dm-1 >> >> \component MyLayout >> >> \MyHeader{Seconde}{17}{08}{2017}{Devo

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-19 Thread Fabrice Couvreur
] {#where \\ {#time}}}] \stoptexdefinition \stopenvironment ### dm-1.tex ### \startcomponent dm-1 \component MyLayout \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m} \input knuth \stopcomponent 2017-08-19 1:29 GMT+02:00 Jeong Dal <hak...@me.com>: > Hi, Otar

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Fabrice Couvreur
I turn around !! It does not work 2017-08-19 1:15 GMT+02:00 Rik <r...@panix.com>: > On 2017-08-18 19:01, Fabrice Couvreur wrote: > > If I test this file, it does not work > > % macros=mkvi > > \startcomponent dm-1 > > \environment MyLayout > >

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Rik
On 2017-08-18 19:01, Fabrice Couvreur wrote: If I test this file, it does not work % macros=mkvi \startcomponent dm-1   \environment MyLayout   \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m}   \dorecurse{20}{\input knuth}   \math{x^2+4x+5=0} \stopcomponent 2017-08-19 0:23

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Fabrice Couvreur
Hi Aditya it does not work 2017-08-19 1:01 GMT+02:00 Fabrice Couvreur <fabrice1.couvr...@gmail.com>: > If I test this file, it does not work > > % macros=mkvi > > \startcomponent dm-1 > > \environment MyLayout > > \MyHeader{Seconde}{17}{08}{2

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Fabrice Couvreur
If I test this file, it does not work % macros=mkvi \startcomponent dm-1 \environment MyLayout \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m} \dorecurse{20}{\input knuth} \math{x^2+4x+5=0} \stopcomponent 2017-08-19 0:23 GMT+02:00 Rik Kabel <c

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Rik Kabel
ndstyle=\ssx]   {Lycée JANSON DE SAILLY \\ \date[d=#day,m=#month,y=#year]}}]   [{\headerframed[align=flushright, foregroundstyle=\ssx]   {#where \\ {#time}}}] \stoptexdefinition \stopenvironment ## dm-1.tex ## \startcomponent dm-1  

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Fabrice Couvreur
{Lycée JANSON DE SAILLY \\ \date[d=#day,m=#month,y=#year]}}] > [{\headerframed[align=flushright, foregroundstyle=\ssx] > {#where \\ {#time}}}] > > \stoptexdefinition > > \stopenvironment > > ## > dm-1.tex > ## > > \startcomponent dm-1 &g

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Rik Kabel
]}}]   [{\headerframed[align=flushright, foregroundstyle=\ssx]   {#where \\ {#time}}}] \stoptexdefinition \stopenvironment ## dm-1.tex ## \startcomponent dm-1   \environment MyLayout   \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m}   \input knuth \stopcomponent 2017

Re: [NTG-context] About \setupheadertexts : simplify a code

2017-08-18 Thread Fabrice Couvreur
] {#where \\ {#time}}}] \stoptexdefinition \stopenvironment ## dm-1.tex ## \startcomponent dm-1 \environment MyLayout \MyHeader{Seconde}{17}{08}{2017}{Devoir surveillé}{1}{1h\,30m} \input knuth \stopcomponent 2017-08-18 18:44 GMT+02:00 Otared Kavian <ota...@gmail.

Re: [NTG-context] Typesetting all documents in a project

2017-06-11 Thread Henri Menke
\startproduct prd_guide > \project project_guide > \environment env_guide2 > > \startfrontmatter > \stopfrontmatter > > \startbodymatter > \component c_guide.tex > \stopbodymatter > > \startbackmatter > \stopbackmatter > > \stopproduct

[NTG-context] Typesetting all documents in a project

2017-06-11 Thread Mike O'Connor
_guide \project project_guide \environment env_guide2 \startfrontmatter \stopfrontmatter \startbodymatter \component c_guide.tex \stopbodymatter \startbackmatter \stopbackmatter \stopproduct - c_guide.tex - \startcomponent c_guide \project project_guide \starttext \startchapter

Re: [NTG-context] Question about " ! Infinite glue shrinkage inserted from \skip131" error

2017-03-10 Thread Hans Hagen
false \postpon... \page_breaks_process ...the \everybeforepagebreak \c_page_breaks_prevpage \r... ...t \nonoindentation \else \page [\v!preference ] \page_otr_command_check_if... ... l.50 \stopplacefigure 1 % !TEX root =../../Main.tex 2 3 \startcomponent MathModel2 4 \prod

[NTG-context] Question about " ! Infinite glue shrinkage inserted from \skip131" error

2017-03-10 Thread Jeong Dal
% !TEX root =../../Main.tex 2 3 \startcomponent MathModel2 4 \product Main 5 6 \SlideTitle{미적분학} 7 >> \null\vfill 8 자연과 일상생활에서 일어나는 많은 일들의 수학적 모델을 잘 찾아낼 수만 있다면 앞으로의 변화나 예상되는 일들을 정확하게 파악할 수 있을 것이다. 하지만 이런 일들의 정확한 수학적모델을 찾는다는 것은 매우 어려운 일이다. 9 대부분의 경우 어느 정

Re: [NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-04 Thread Benjamin Buchmuller
t, the entire page > including the figure’s rulers, caption, and the regular text prints in red > (but not bold!?) when I incorporate the file via \component … into my > project, but not when I typeset from within \startcomponent … \stopcomponent. > > Since “bold” does no

Re: [NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-04 Thread Hans Hagen
project, but not when I typeset from within \startcomponent … \stopcomponent. Since “bold” does not seem to float the same way, I guess it is related to color handling at page breaks somehow. I already tried to \setupfloats[before=\strut] to “force” black bodyfont right before the figure (at least

[NTG-context] \setupfooter[color=red]: red color spills with float over next page

2016-12-03 Thread Benjamin Buchmuller
\stopplacefigure other text that is moved to the following page as first object, the entire page including the figure’s rulers, caption, and the regular text prints in red (but not bold!?) when I incorporate the file via \component … into my project, but not when I typeset from within \startco

Re: [NTG-context] Building a Component

2016-09-12 Thread Malte Stien
context runs into what seems to be an >> infinite recursion. Here is the file: >> >> >> \project test-project >> \product reference-manual-1 > Move the two lines after \startcomponent.

Re: [NTG-context] Building a Component

2016-09-12 Thread Wolfgang Schuster
finite recursion. Here is the file: \project test-project \product reference-manual-1 Move the two lines after \startcomponent. \startcomponent component-1 \starttext You don’t need \starttext/\stoptext when you use product and component files. Wo

[NTG-context] Building a Component

2016-09-12 Thread Malte Stien
-manual-1 \startcomponent component-1 \starttext \section[c1-s1]{Component 1 Section 1} This is a paragraph in Component 1 Section 1 \stoptext \stopcomponent ...and here is the console when I run it: > context component-1.tex ... ... ... open source > 196 > 198 > component-1.tex

Re: [NTG-context] ntg-context Digest, Vol 145, Issue 61

2016-07-21 Thread Hans Hagen
ocessed file starts with: ++ \definehead [intro] [chapter] \setuphead [intro] [number=no,alternative=middle,style=\tfa \bf] \startcomponent TD_Ch0-Intro.tex \intro[bookmark=,label=,list={Introduction},marking=,reference=ch:Intro,title={Introduction}] shouldn't that be

Re: [NTG-context] ntg-context Digest, Vol 145, Issue 61

2016-07-21 Thread Robert Blackstone
gt;> l.191 \stopintro >> + >> >> The processed file starts with: >> ++ >> \definehead [intro] [chapter] >> \setuphead [intro] [number=no,alternative=middle,style=\tfa \bf] >> >> \startcomponent TD

[NTG-context] What is wrong with \stopintro?

2016-07-21 Thread Robert Blackstone
processed file starts with: ++ \definehead [intro] [chapter] \setuphead [intro] [number=no,alternative=middle,style=\tfa \bf] \startcomponent TD_Ch0-Intro.tex \intro[bookmark=,label=,list={Introduction},marking=,reference=ch:Intro,title={Introduction}] +++

Re: [NTG-context] What is wrong with \stopintro?

2016-07-21 Thread Hans Hagen
... l.191 \stopintro + The processed file starts with: ++ \definehead [intro] [chapter] \setuphead [intro] [number=no,alternative=middle,style=\tfa \bf] \startcomponent TD_Ch0-Intro.tex \intro[bookmark=,label=,list={Introduction},marking=,reference=ch:In

Re: [NTG-context] Product-component structure

2016-07-11 Thread Procházka Lukáš Ing .
e of components; can be compiled individually, but sections are not numbered from the point of view of the final document (= book.tex) ("globally") but "locally" from the point of view of just comp01.tex \environment styles.sty \startcomponent * ... \stopcomponent Resume: - E

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
roblem with puttins \environment before \startcomponents is that you can’t check for the *component mode which is enabled after the environment was loaded. So, one should use: \startcomponent * \environment env ... \stopcomponent for both components and pr

Re: [NTG-context] Product-component structure

2016-06-25 Thread Hans Hagen
ileonce }, [v_product] = { "none", processfilenone }, [v_component] = { "many", processfilemany }, } } Then, why is the product file processed multiple times? The rules for a component files are applied *after* \startcomponent which isn’t the case for the

Re: [NTG-context] Product-component structure

2016-06-25 Thread Aditya Mahajan
= { "none", processfilenone }, [v_component] = { "many", processfilemany }, } } Then, why is the product file processed multiple times? The rules for a component files are applied *after* \startcomponent which isn’t the case for the example where in the first iteration the &quo

Re: [NTG-context] Product-component structure

2016-06-25 Thread Wolfgang Schuster
= { "many", processfilemany }, } } Then, why is the product file processed multiple times? The rules for a component files are applied *after* \startcomponent which isn’t the case for the example where in the first iteration the "text" rules are applied and

Re: [NTG-context] [SOLVED] searching in subdirectories with project structure

2016-05-05 Thread Javier M Mora
\environment envi_thesis blah blah \startbodymatter \component comp_chapter1 \component comp_chapter2 blah blah \stopbodymatter \stopproduct comp_chapter1.tex \startcomponent comp_chapter1 \product prod_thesis \environment envi_chapter1 \chapter

Re: [NTG-context] searching in subdirectories with project structure

2016-05-05 Thread Javier M Mora
(...) /tables/ /table1.tex /table2.tex (...) /comp_chap2/ /comp_chap2.tex /envi_chap2.tex /images/ /image1b.jpg /image2b.jpg (...) /tables/ /table1b.tex /table2b.tex (...) (...) [...] comp_chap1.tex has: \startcomponent comp_chap1.tex

[NTG-context] searching in subdirectories with project structure

2016-05-05 Thread Javier M Mora
has: \startcomponent comp_chap1.tex \product prod_thesis \environment envi_chap1 blah blah blah \placefigure[here][fig:img1]{img1}{ \externalfigure[image1.jpg] } blah blah blah \input tables/table1 blah blah

Re: [NTG-context] Page number woes

2016-03-15 Thread Wolfgang Schuster
now (production in sensitive phase), but if you think the problem will go away with an update, I'll do it. Move your intro text after the \startfrontmatter command everything before it doesn’t belong to any sectionblock. You can also omit \startext and \stoptext commands when you \startcompon

Re: [NTG-context] cross-references between documents in a project (using \useexternaldocument)

2015-09-09 Thread Jens Bertram
][XR Product Two] \nopdfcompression \startproject xr-proj \product xr-prod1 \product xr-prod2 \stopproject \startcomponent xr-comp2-1 \starttext plain\\ ABOUT: \about[xr1::plain]\\ IN: \in[xr1::plain]\\ AT: \at[xr1::plain] page2\\ ABOUT: \about[xr1::pagetwo]\\ IN: \in[xr1::pagetwo]

[NTG-context] Sectioning and structure

2015-09-07 Thread Fabrice Couvreur
chapter-1.tex \startcomponent chapter-1 \component activities-1 \component synthesis-1 \component training-1 \stopcomponent # Thanks, Fabrice ___ If your question

[NTG-context] Output compilation

2015-08-12 Thread Fabrice Couvreur
titlepage \component contents \stopfrontmatter \startbodymatter \component chapter-1 \stopbodymatter \stopproduct ## \startcomponent chapter-1 \component activities \component synthesis \stopcomponent

Re: [NTG-context] Output compilation

2015-08-12 Thread Fabrice Couvreur
Hi Wolfgang, In fact, I had already tried what you propose without success. But I just realized that the contents of my file is : \startcomponent activities ... \stopcomponent and I forgot *\project manual * that contains : \environment my-fonts \environment my-layout \environment my

Re: [NTG-context] cross-references between documents in a project (using \useexternaldocument)

2015-08-06 Thread tala...@fastmail.fm
project_xref \startcomponent xref1 \starttext \chapter[cross]{Cross referencing} \chapter[lorem]{Lorem} Lorem ipsum dolor sit amet, consectetur adipiscing elit \in{Chapter}[lorem]. \stoptext \stopcomponent % component2 [xref2] \project project_xref \startcomponent xref2 \useexternaldocument[xrf

[NTG-context] cross-references between documents in a project (using \useexternaldocument)

2015-08-05 Thread tala...@fastmail.fm
\product prd_xref \stopproject % environment \startenvironment env_xref \setupinteraction [state=start, style=, color=blue, contrastcolor=, menu=on, title=Cross referencing Test File, author=Gerard Verhaag] \stopenvironment % component1 [xref1] \project project_xref \startcomponent

[NTG-context] local environment?

2015-08-04 Thread tala...@fastmail.fm
\startenvironment envA % the definitions \stopenvironment # EnvironmentB \startenvironment envB % the definitions \stopenvironment # ComponentA \environment envA \product MyProduct \startcomponent ComponentA \starttext … \stoptext # ComponentB \environment envB \product MyProduct

[NTG-context] Component of a product (correction!)

2015-06-18 Thread Procházka Lukáš Ing . - Pontex s . r . o .
Hello, suppose the following case: Book.mkiv \startproduct * \component A.mkiv \component B.mkiv \stopproduct A.mkiv \startcomponent * \section{A} \stopcomponent B.mkiv \startcomponent * \section{B} \stopcomponent When compiling Book.mkiv, I'm

[NTG-context] Component of a product

2015-06-18 Thread Procházka Lukáš Ing . - Pontex s . r . o .
Hello, suppose the following case: Book.mkiv \startproduct * \component A.mkiv \component B.mkiv \stopproduct A.mkiv \startcomponent * \section{A} \stopcomponent B.mkiv \startcomponent * \section{B} \stopcomponent When compiling Book.mkiv, I'm getting

Re: [NTG-context] SyncTeX and mkiv

2015-04-08 Thread Otared Kavian
). It even works if it is not in the first line, for example: Product file: \startproduct pd-test \enabledirectives [system.synctex] \component 01-intro \stopproduct Component: \startcomponent 01-intro Hi there, can you show me this sentence in the source file? \stopcomponent

Re: [NTG-context] SyncTeX and mkiv

2015-04-07 Thread Thomas Floeren
works if it is not in the first line, for example: Product file: \startproduct pd-test \enabledirectives [system.synctex] \component 01-intro \stopproduct Component: \startcomponent 01-intro Hi there, can you show me this sentence in the source file? \stopcomponent But, indeed, it doesn’t work

Re: [NTG-context] mkiv versus mkii: whitespace issues

2015-03-15 Thread Gerben Wierda
][margin=1.3em,pagecommand=\gobbleoneargument] \define[1]\ChapterAbstract{\writetolist[chaptertext]{}{\start\itx#1\stop}} \stopenvironment = test.tex mkii \showgrid \startcomponent c_loosely \product prd_book \project

  1   2   3   4   >